x1439 client - [PR] Treatment type on the SGP management page to help breakdown the worfklows#1194
Conversation
…9 updateWorkXeniumStudy mutation (3bcf5228) from devel into treatment branch
…to fix the timing issue
…data, reflecting the real UI and backend behaviour
…lect must be the Formik array of strings; not an array of option objects because the component handles mapping internally
a81e95b to
2ad595d
Compare
…page-to-help-breakdown-the-worfklows
…ss UI in work allocation component
… Number form of SGP Management page after feedback
…tion table of SGP Management page after feedback
…on table of SGP Management page after feedback
…sage in SGP management page
…ion of SGP management page
…, and coloured pills in SGP management page
…ta in SGP management page
…ment types config, to prevent showing incorrect config values after navigation within the app
…eniumAnalyser.cy.ts
…y in cypress/e2e/pages/xeniumAnalyser.cy.ts
…umQC mutation in visiumQC spec
…es, flat/flatMap, Promise, etc.) in Cypress tests so TypeScript/IDE no longer reports missing lib typings for those APIs
…page-to-help-breakdown-the-worfklows
| image: cypress/browsers:node18.12.0-chrome106-ff106 | ||
|
|
||
| options: --user 1001 | ||
| image: cypress/browsers:node-22.14.0-chrome-134.0.6998.165-1-ff-136.0.3-edge-134.0.3124.85-1 |
There was a problem hiding this comment.
I would leave this for a separate PR and handle the Node upgrade there, including upgrading the build Node version as well as the github actions versions
At the moment, the tests are running with a different Node version from the one used to build the image
There was a problem hiding this comment.
Test use the version from .nvmrc which is 22.14.0 and that matches this image version.
I will still extract the change to another PR as you asked.
| .then((res) => { | ||
| // revalidate route loader so the configuration page sees server-side updates | ||
| try { | ||
| revalidator.revalidate(); |
There was a problem hiding this comment.
do you mean the server response by 'the server-side updates'?
| mockCreateObjectURL(); | ||
|
|
||
| // Mock URL.createObjectURL for jsdom environment | ||
| mockCreateObjectURL(); |
| // treatment type pills rendered in the treatment cell | ||
| // find pill spans anywhere in the row | ||
| const allSpans = row!.querySelectorAll('span'); | ||
| const pillSpans = Array.from(allSpans).filter((p) => { |
There was a problem hiding this comment.
If you're using a component specifically for test assertions, the convention is to add a data-testid attribute so it can be reliably selected and tested. This makes it easier to target elements in tests without relying on CSS classes or DOM structure.
Changes proposed in this pull request
User feedback: Treatment types should appear after Work Type
(except configuration page tab; they are in alphabetical order)
Not included: "Editable on the final SGP tracking page (later story)"
Miscellaneous:
Instructions for Reviewers
[All PRs] - Confirm PR template filled
[Feature Branches] - Review code
[Production Merges to
main]- Check story numbers included
- Check for debug code
- Check version